PR Summary

This PR introduces a change to how the torch library is imported in the client module. Instead of a direct import, the torch import is wrapped in a try/except block. If importing torch fails for any reason, the variable is set to None. This adjustment makes the module more resilient in environments where torch might not be installed without breaking the rest of the application.

Additionally, version increments in the project files ensure consistency across the version declarations, aligning the project version between documentation and runtime but these version changes are not the primary focus of this PR.

Test Suggestions

• Verify that the client module functions normally when torch is not installed by simulating an ImportError.
• Test that when torch is available, it is imported and used correctly within the client module.
• Ensure that any subsequent accesses to torch in the application handle the case when torch is None, avoiding runtime errors.